Explores lock-free code by focusing on creating a lock-free queue.

The Boost.Thread library, which enables the use of multiple threads of execution with shared data in portable C++ code, has undergone some major changes.

Discusses the usage of the volatile keyword in multithreaded C++ programs.

Motivates and illustrate best practices for using threads - techniques that will make concurrent code easier to write correctly and to reason about with confidence.

A thread pool hides a lot of details, but to use it effectively some awareness of some things a pool does under the covers is needed to avoid inadvertently hitting performance and correctness pitfalls.

Explains how to use lock hierarchies to avoid deadlock by assigning each shared resource a level that corresponds to its architectural layer.

Explains how to accurately analyze the real performance of parallel code and lists some basic considerations and common costs.

Argues that for concurrent programming to become mainstream, threads must be discarded as a programming model. Nondeterminism should be judiciously and carefully introduced where needed, and it should be explicit in programs.

This article makes the case that a consistent mental model is needed to talk about concurrency.

Explains that deadlock can happen whenever there is a blocking (or waiting) cycle among concurrent tasks.